The DBMS must notify appropriate individuals when account disabling actions are taken.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-52195	O112-C2-020600	SV-66411r2_rule		Medium

Description
When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events that affect user accessibility and application processing, applications must audit account disabling actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that application accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. Note that user authentication and account management must be done via an enterprise-wide mechanism whenever possible. Examples of enterprise-level authentication/access mechanisms include, but are not limited to, Active Directory and LDAP. This requirement applies to cases where it is necessary to have accounts directly managed by Oracle. However, notwithstanding how accounts are managed, the DBMS must support the requirement to notify appropriate individuals upon the disabling of an account. Indeed, in a configuration where accounts are normally managed externally, the manipulation of an Oracle account may indicate hostile activity.

Description

When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events that affect user accessibility and application processing, applications must audit account disabling actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that application accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. Note that user authentication and account management must be done via an enterprise-wide mechanism whenever possible. Examples of enterprise-level authentication/access mechanisms include, but are not limited to, Active Directory and LDAP. This requirement applies to cases where it is necessary to have accounts directly managed by Oracle. However, notwithstanding how accounts are managed, the DBMS must support the requirement to notify appropriate individuals upon the disabling of an account. Indeed, in a configuration where accounts are normally managed externally, the manipulation of an Oracle account may indicate hostile activity.

STIG	Date
Oracle Database 11.2g Security Technical Implementation Guide	2015-03-26

Details

Check Text ( C-54253r1_chk )
Check DBMS settings to determine whether it will notify appropriate individuals when account disabling actions are taken. If the DBMS does not notify appropriate individuals when account disabling actions are taken, this is a finding.

Fix Text (F-57013r2_fix)
Working with the DBA and site management, determine the appropriate individuals (by job role) to be notified. If Oracle Audit Vault is available, configure it to notify the appropriate individuals when accounts are disabled. If Oracle Audit Vault is not available, configure the Oracle DBMS's auditing feature to record account-disabling activity. Create and deploy a mechanism, such as a frequently-run job, to monitor the SYS.AUD$ table or the audit trail file, whichever is in use, for these records and to notify the appropriate individuals.

Fix Text (F-57013r2_fix)

Working with the DBA and site management, determine the appropriate individuals (by job role) to be notified.

If Oracle Audit Vault is available, configure it to notify the appropriate individuals when accounts are disabled.

If Oracle Audit Vault is not available, configure the Oracle DBMS's auditing feature to record account-disabling activity. Create and deploy a mechanism, such as a frequently-run job, to monitor the SYS.AUD$ table or the audit trail file, whichever is in use, for these records and to notify the appropriate individuals.